For DOS 2.5 or no command/parameter line.
If you have the 'no-bundle' version it is necessary to run the driver before loading MCP, i.e.:
L {return}
D:MIDICAR.DRV {return}
L {return}
D:MCP.EXE {return}
Of course, the drivers must be on the floppy 
.
In the 'bundle' version, the driver is already 'tacked on' to MCP, so all you need to do is run MCP.EXE.
You can prepare such a 'bundle' version yourself. Just combine the corresponding driver and the 'no-bundle' version of MCP into one file.
XDOS
Personally, I recommend XDOS as it is much lighter and has some very useful features, which are:
- batch files
- the ability to modify memory
- passing parameters to the program.
The first useful feature is obvious - the ease of running MCP.
To prepare such a file under XDOS, get a simple editor 
or from the command line type:
D:>COP E; MCP.CMD {return} " {return} {quote - is required for XDOS batch files}
MIDICAR.DRV {return}
MCP.EXE {return}
{press CTRL+3 to exit}
To run such a file you only need to type its name (without extension), i.e.
D:>MCP {return}
.
The second useful feature is the built-in, very simple monitor.
Why am I mentioning it
MIDICar does not perform a reset on its own when the computer is switched on.
This can result in it being detected incorrectly. To prevent this, under XDOS, issue two commands:
D:>=xxxx 03 {in place of xxxx, enter the address you have set on the jumpers in MIDICar}
D:>=82 xxxx {as above}
Of course, you can add these two lines to a batch file, just before loading the driver.
What do these lines do
The first: "=xxxx 03" resets the MIDICar device.
The second: "=82 xxxx" sets (for the MIDICAR.DRV driver) the device address, so that no autodetection is performed.
The above two lines, are the equivalent of the Spartan POKE and (nota bene) under SDX they should also be executed.
For DOS with a command line or the ability to pass parameters to programs (e.g. XDOS, MyDOS, RealDOS, SDX) you can run MCP with additional parameters, including
/Axxxx
This switch causes the above 'poke' to be executed by the MCP loader. In place of 'xxxx' enter the address set on MIDICar's jumpers
/Dx:drivername.drv
For MCP 'no-bundle' allows the driver to be loaded from the indicated location, with the indicated name. For 'bundle' the integrated driver will be overwritten (in memory) by the one indicated in the switch.
SDX
Here there is such a little catch with the naming of the switch itself, i.e. '/Dx:' Namely, the letter 'D' is - in addition to indicating the switch - also the name of the device, i.e. DISK. As you know, under SDX the drive/drive letters can be described in different ways, i.e.
D1: = A: = DA:
B: = D2: = DB:
DJ: = D10: = J:
etc.
As can be seen, with the short drive designations A: B: ... there will be a problem with the '/Dx:' switch. You can't write '/A:driver' Therefore, you have to use a 'long' notation wanting to refer to another drive, e.g.
D:>X MCP.EXE /D5:>MCP>MIDICAR.DRV /AD580
D:>X MCP.EXE /DA:MIDIBOX.DRV
D:>X MCP.EXE /DH:MIDIMATE.DRV D1:
'X' is used ONLY under SDX!.
In the last example, the "D1:" at the end is not a switch, but a message to the MCP that, when started, it is to read a directory from the indicated drive, i.e. "D1:" You can indicate the track or also the name of the MID file to be read. Remember to ALWAYS specify the full path, i.e.
DE:>GAMES>ATARI>
DE:>GAMES>ABUSE>01INTRO.MID
DA:APIDYA.MID
Unfortunately, the MCP loader does not search the PATH environment variable - this is to maintain compatibility with DOS other than Sparta DOS (X) Hence, it may not be possible or very difficult to achieve certain actions, such as associating files with the MCP program. Therefore, MCP has an integrated, very convenient file selector 🙂
I hope that I have not made a glaring mistake anywhere and that, the tips described here will serve.
PeBe
